Repository navigation
Switch Discourse category for repository addition discussions to Core Development - #1934
StanFromIreland wants to merge 1 commit into
Conversation
Documentation build overview
|
|
The policy text came from the SC, so probably worth checking in with them? It was added in #1036 which says:
Joannah had suggested:
This is an important point. I think Committees was chosen as it's more clearly a "committer channel", and because the core team is more likely to be watching that than Core Development? And creating a new repo is mainly about how we manage our internal org, so I don't think we necessarily need external input. (The discussion happens in the open, so external folk can still create another topic if needed.) Other things, like discussing with project maintainers about getting involved with snake_pit, should absolutely be done in open channels. But I don't think repo policy moves necessarily need that. |
I don't think we need to require they be in the Commiters category, which is restricted to core team members. As such I suggest we switch to the Core Development category. This is quite minor, so I think we can avoid a SC issue, if these is agreement.